Efficient evaluation of index screening predicates

ABSTRACT

Techniques are provided for processing a query using an index. It is determined whether a number of consecutive keys that evaluate to a false-positive when applying a screening predicate in the query exceeds a false-positive predefined value. One or more keys in the index are skipped in response to determining that the number of consecutive keys exceeds the false-positive predefined value.

BACKGROUND

1. Field

Embodiments of the invention relate to efficient evaluation of indexscreening predicates.

2. Description of the Related Art

Relational DataBase Management System (RDBMS) software may use aStructured Query Language (SQL) interface. The SQL interface has evolvedinto a standard language for RDBMS software and has been adopted as suchby both the American National Standards Institute (ANSI) and theInternational Standards Organization (ISO).

A RDBMS uses relational techniques for storing and retrieving data in arelational database. Relational databases are computerized informationstorage and retrieval systems. Relational databases are organized intotables that consist of rows and columns of data. The rows may be calledtuples or records or rows. A database typically has many tables, andeach table typically has multiple records and multiple columns.

A table in a database can be accessed using an index. An index is anordered set of references (e.g., pointers) to the records in the table.The index is used to access each record in the table using a key (i.e.,one of the fields or attributes of the record, which corresponds to acolumn). The term “key” may also be referred to as “index key”. Withoutan index, finding a record requires a scan (e.g., linearly) of an entiretable. Indexes provide an alternate technique to accessing data in atable. Users can create indexes on a table after the table is built. Anindex is based on one or more columns of the table.

A query may be described as a request for information from a databasebased on specific conditions. A query typically includes one or morepredicates. A predicate may be described as an element of a searchcondition that expresses or implies a comparison operation (e.g., A=3).

Indexable predicates may be described as predicates that are applied toindex columns (i.e., columns used to build an index). An indexablepredicate may be described as either a matching predicate or a screeningpredicate. Matching predicates may be described as having a constrainton leading index columns and, hence, may be used to define the searchrange of index scans. Screening predicates, on the other hand, are usedto provide additional filtering once a key is looked up in an indexscan. For example, let IX1 be an index on columns C1 and C2. In Query(1), the predicate 'C1 BETWEEN 1 AND 95′ is a matching predicate, andpredicate 'C2 BETWEEN 50 AND 52′ is a screening predicate. Query (1)SELECT * FROM T WHERE C1 BETWEEN 1 AND 95  AND C2 BETWEEN 50 AND 52;

An example is provided below to explain the nature of the problem. Inthe example, table T is a table of transactions in year 2003, and indexIX1 is a 2-column index over date and amount for table T. The Query (2)finds all the ‘high volume’ transactions in the first half of year 2003.Suppose an optimizer of the RDBMS exploits index IX1 for the scan oftable T. In this example, the 1-column matching index scan has poormatching selectivity (roughly 50%) and high screening selectivity(assuming 2%). Query (2) SELECT * FROM T WHERE date BETWEEN ‘2003-01-01’AND ‘2003-06-30’ <- 50% selectivity AND amount >= 300000; <- 2%selectivity

In this example, table T contains one million records. The index scanfor the matching predicate results in a scan of roughly 500,000 keys.For each key found to meet the matching predicate, the screeningpredicate is applied, which, results in 500,000 evaluations of thescreening predicate. However, less than 20,000 keys actually survive thescreening predicate in this example.

A B-tree index is a binary tree that may be used to store the referencesto the records in a table. FIG. 1 illustrates a sample B-tree index 100that represents the results of Query (2). In the B-tree index 100, thebottom level contains “leaves” or “leaf pages”. Each leaf page containsa list of keys. Each leaf page includes a pointer to a next leaf page.For the matching range, there are a large number of false-positives. Afalse-positive may be described as a key that results in a match for thematching predicate but not for the screening predicate.

Thus, there is a need in the art for efficient evaluation of indexscreening predicates.

SUMMARY

Provided are a method, article of manufacture, and system for processinga query using an index. It is determined whether a number of consecutivekeys that evaluate to a false-positive when applying a screeningpredicate in the query exceeds a false-positive predefined value. One ormore keys in the index are skipped in response to determining that thenumber of consecutive keys exceeds the false-positive predefined value.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers representcorresponding parts throughout:

FIG. 1 illustrates a sample B-tree index.

FIG. 2 illustrates details of a computer architecture in which certainembodiments may be implemented.

FIG. 3 illustrates logic performed by an enable module in accordancewith certain embodiments.

FIGS. 4A and 4B illustrate logic performed by a detection module inaccordance with certain embodiments.

FIGS. 5A, 5B, and 5C illustrate logic performed by a skipping module inaccordance with certain embodiments.

FIG. 6 illustrates leaf pages in a B-tree index in accordance withcertain embodiments.

FIG. 7 illustrates an architecture of a computer system that may be usedin accordance with certain embodiments.

DETAILED DESCRIPTION

In the following description, reference is made to the accompanyingdrawings which form a part hereof and which illustrate severalembodiments. It is understood that other embodiments may be utilized andstructural and operational changes may be made without departing fromthe scope of embodiments of the invention.

FIG. 2 illustrates details of a computer architecture in which certainembodiments may be implemented. A client computer 200 is connected via anetwork 290 to a server computer 220. The client computer 200 includessystem memory 204, which may be implemented in volatile and/ornon-volatile devices. One or more client applications 210 (i.e.,computer programs) are stored in the system memory 204 for execution bya processor (e.g., a Central Processing Unit (CPU)) (not shown).

The server computer 220 includes system memory 222, which may beimplemented in volatile and/or non-volatile devices. System memory 222stores a data store manager 230 (e.g., a Relational DataBase ManagementSystem (RDBMS)), an index manager 240, and one or more serverapplications 250. The data store manager 130 includes an enable module232 and may include one or more other components 234. The index manager240 includes a detection module 242 and a skipping module 244. The indexmanager 240 may include one or more other components 246. These computerprograms that are stored in system memory 222 are executed by aprocessor (e.g., a Central Processing Unit (CPU)) (not shown). Theserver computer 220 provides the client computer 200 with access to datain a data store 270.

In alternative embodiments, the computer programs may be implemented ashardware, software, or a combination of hardware and software.

The client computer 200 and server computer 220 may comprise anycomputing device known in the art, such as a server, mainframe,workstation, personal computer, hand held computer, laptop telephonydevice, network appliance, etc.

The network 290 may comprise any type of network, such as, for example,a Storage Area Network (SAN), a Local Area Network (LAN), Wide AreaNetwork (WAN), the Internet, an Intranet, etc.

The data store 270 may comprise an array of storage devices, such asDirect Access Storage Devices (DASDs), Just a Bunch of Disks (JBOD),Redundant Array of Independent Disks (RAID), virtualization device, etc.

In conventional systems, keys are evaluated in the order of theirpresence for the screening predicate. With embodiments, intelligent keyskipping and evaluation logic is provided. A certain number of keysqualified by matching predicates are skipped without being fetched andevaluated for screening predicates based on the knowledge that many keysmay be false-positive keys and that those keys tend to be consecutive intheir presence (i.e., this range of false-positive keys may also bereferred to as a “hole” of false-positive keys). Also, keys are storedin sorted order. The matching index column is the primary sorting order,and the index screening column is the secondary sorting order. In casesin which the column value for the matching column is frequentlyrepeated, certain keys may be skipped within each repeating range ofindex matching columns, as long as potentially qualified keys for thescreening predicate is not skipped. This can be ensured by checking thatskipping is used within the same index matching column range.

Embodiments provide an enable module 232, a detection module 242, and askipping module 244.

FIG. 3 illustrates logic performed by the enable module 232 inaccordance with certain embodiments. Control begins in block 300 withthe enable module 232 receiving a query. In block 302, the enable module232 determines whether the index matching predicate filtering is notgood and the index screening predicate filtering is good for the query.If so, then processing continues to block 304, otherwise, processingcontinues to block 308. That is, the enable module 232 checks for thefiltering of the index matching predicates and index screeningpredicates. Filtering may be described as an estimate of the resultsthat may be obtained by applying a predicate relative to the originalnumber of keys against which the predicate is applied. Filtering isestimated using statistics, rather than by actually applying thepredicate. For example, if it is estimated that applying the matchingpredicate to 100 keys would result in 10 matches, then the filtering issaid to be 1/10(i.e., 10/100). If the filtering for index matchingpredicates is poor (i.e., a large number of results are estimated, suchas 90/100), but the index screening predicate is very selective (i.e., asmall number of results are estimated, such as 5/100), the enable module232 recognizes that there are a lot of holes of false-positive keys thatmay be skipped.

In block 304, the enable module 232 determines whether an index full keycardinality divided by an index matching column cardinality is greaterthan a first predefined value (also referred to as a “ratio” predefinedvalue). If so, processing continues to block 306, otherwise, processingcontinues to block 308. That is, the enable module 232 uses certainstatistical information, such as the index full key cardinality and thematching column cardinality. The index full key cardinality may bedescribed as a number of distinct key values for all index columns(e.g., if the index has two columns, and there are key values A, A, B ina first column and A, C, C in a second column, then the index full keycardinality is three). The matching column cardinality may be describedas a number of distinct key values for a column associated with amatching predicate. For example, if the first column is a matchingcolumn, then the matching column cardinality for the first column wouldbe two. If the ratio of the index full key cardinality to the matchingcolumn cardinality is high, then the enable module recognizes that therepeat rate of matching column values is high (i.e., for consecutivekeys in the leaf pages, it is likely that many have the same values).

In block 306, the enable module 232 enables skipping logic that isperformed by the skipping module 244. In certain embodiments, enablingthe skipping logic includes setting a skipping mode indicator toindicate that skipping logic is to be enabled. Then, the detectionmodule 242 checks the skipping mode indicator, and if the skipping modeindicator is set to indicate that skipping is enabled, the detectionmodule 242 performs certain processing, which may include setting astart skipping indicator to indicate that skipping is to be performed.The start skipping indicator is checked by the skipping module 244.Thus, if the conditions of blocks 302 and 304 are met, skipping logic isenabled by the enable module 232. In block 308, other processing isperformed.

FIGS. 4A and 4B illustrate logic performed by the detection module 242in accordance with certain embodiments. Control begins in block 400 withthe detection module 242 determining whether the skipping mode indicatoris set to indicate that skipping is enabled. If so, processing continuesto block 402, otherwise, processing continues to block 420 and otherprocessing is performed. In block 402, the detection module 242initializes a number of consecutive false-positive keys to be zero. Inblock 404, the detection module 242 selects a next key in a matchingrange of the matching predicate, with a first key selected being at acurrent position. The selected key may be referred to as a “currentkey”. In block 406, the detection module 242 determines whether all keyshave been selected. If so, processing ends, otherwise, processingcontinues to block 408.

In block 408, the detection module 242 determines whether the currentkey evaluates to a false-positive when applying a screening predicate.If so, processing continues to block 410, otherwise, processingcontinues to block 416. In block 410, the detection module 242increments the number of consecutive false-positive keys by one. Inblock 412, the detection module 242 determines whether the number ofconsecutive false-positive keys is greater than a second predefinedvalue (also referred to as “false-positive” predefined value). If so,processing continues to block 414, otherwise, processing loops back toblock 404 of FIG. 4A to select the next key, if there is one. In block414, the detection module 242 starts the skipping logic and processingcontinues to block 500 of FIG. 5A. In certain embodiments, the detectionmodule 242 sets a start skipping indicator to indicate that skipping isto be performed. The start skipping indicator is checked by the skippingmodule 244.

Block 416 is reached when the current key has evaluated to be qualifiedagainst the screening predicate, and the detection module 242 resets thenumber of consecutive false positive keys to be zero. In block 418, thedetection module 242 returns the key to a caller, such as the data storemanager 230 or another component 234 of the data store manager 230. Fromblock 418, processing loops back to block 404 to select the next key, ifthere is one.

Thus, the detection module 242 is capable of autonomically detectingwhether the current key is within a hole of false-positive keys. If so,the detection module 242 invokes the skipping module 244, otherwise, thenext key is fetched and evaluated.

FIGS. 5A, 5B, and 5C illustrate logic performed by the skipping module244 in accordance with certain embodiments. Control begins at block 500with the skipping module 244 determining whether skipping is in effect.In certain embodiments, this is done by checking the value of the startskipping indicator. If skipping is in effect, processing continues toblock 502, otherwise, processing continues to block 404 of FIG. 4A.

In block 502, the skipping module 244 jumps to the next key by skippinga certain number of keys. In block 504, the skipping module 244determines whether the jump went beyond the last key in the matchingpredicate range. If so, processing continues to block 518 of FIG. 5C,otherwise, processing continues to block 506.

In block 506, the skipping module 244 determines whether the matchingcolumn value of the current key is the same as a last evaluated key. Ifthey are the same, processing continues to block 508, otherwise,processing continues to block 518 of FIG. 5C. In block 508, the skippingmodule 244 determines whether the screening column value of the currentkey is within a range of the screening predicate. If so, processingcontinues to block 510, otherwise, processing continues to block 518 ofFIG. 5C. Thus, if the conditions of blocks 506 or block 508 are true,then processing continues to determine whether the skipping wassuccessful.

In block 510, the skipping module 244 determines whether potentialqualified keys have been skipped. If so, processing continues to block518 of FIG. 5C, otherwise, processing continues to block 512. It can bedetermined whether potential qualified keys have not been skipped basedon the type of the predicate (e.g., an “=” predicate or a “between”predicate), and based on the type of the index (e.g., unique index ornonunique index). For example, with reference to Query (2) (below), if akey has value 300001, then qualified keys have not been skipped, but ifthe key has the value 300010, it is possible that some qualified keyshave been skipped.

In block 512, the skipping module 244 determines whether the key isqualified based on evaluating the screening predicate. If so, processingcontinues to block 514, otherwise, processing continues to block 502 ofFIG. 5A to perform another skip. Thus, if the evaluation of the keyright after the skipping shows that the key is inside the hole offalse-positive keys and potentially qualified keys have not beenskipped, then the skipping module 244 performs another skip.

In block 514, the skipping module 244 returns the key to a caller, suchas the data store manager 230 or another component 234 of the data storemanager 230. In block 516, the skipping module 244 stops the skippinglogic. In certain embodiments, the skipping logic is stopped by settingthe start skipping indicator to indicate that skipping is not to beperformed. From block 516, processing continues to block 404 of FIG. 4A.

Thus, if the evaluation of the key right after the skipping shows thatthe key is qualified and no potentially qualified keys have beenskipped, the key is returned to the to the data store manager 230 oranother component 234 of the data store manager 230 and the next key isevaluated without any skipping. Then, the skipping module 244 resumesskipping after a predefined number of consecutive keys are evaluated tobe false-positive, which the detection module 242 detects.

In block 518 of FIG. 5C, the skipping module 244 backs up to the keyfrom which the last skip was made. In block 520, the skipping module 244adjusts a skipping interval. In block 522, a number of skipping failuresis incremented by one. In block 524, the skipping module 244 determineswhether the number of skipping failures is greater than a thirdpredefined value (also referred to as “skipping failures” predefinedvalue). If so, processing continues to block 526, otherwise, processingcontinues to block 502 of FIG. 5A to perform another skip. In block 526,the skipping module 244 stops the skipping logic. From block 526,processing continues to block 404 of FIG. 4A. Thus, if the evaluation ofa key right after the skipping reveals that the current skip interval istoo big. In this case, a decreased skip interval is set. Then, theskipping module 244 backs up to the previous key position and attemptsanother skip with the scaled down skip interval. In certain embodiments,if the second attempt also fails, the keys are evaluated one afteranother, until the skipping is started again by the detection module242.

In block 526, the skipping module 244 stops the skipping logic. Fromblock 526, processing continues to block 404 of FIG. 4A.

Thus, the skipping module 244 automatically adjusts the skippinginterval based on the results of a last set of evaluations. In certainembodiments, the skipping interval does not result in leaping beyond acurrent page, unless there is knowledge that the hole of false-positivekeys extends beyond the current page. In certain embodiments, an initialskipping interval is determined such that the key that is jumped to isthe highest key on a page (i.e., the last key on the page). Since thekeys are ordered on the page, it is possible to go to the highest key onthe page without fetching other keys in between the current key and thehighest key on the same page. To move to a next page, the skippingmodule 244 uses a next page pointer in a leaf page.

In various embodiments, the first predefined value, the secondpredefined value, and the third predefined value may be the same ordifferent values.

Merely to enhance understanding of embodiments of the invention, anexample will be provided with reference to Query(2). The example is notintended to limit the embodiments in any manner. Query (2) is providedagain for easy reference. Query (2) SELECT * FROM T WHERE date BETWEEN‘2003-01-01’ AND ‘2003-06-30’ <-- 50% selectivity  AND amount >= 300000;<-- 2% selectivity

FIG. 6 illustrates leaf pages 600, 602, 604, 606 in a B-tree index inaccordance with certain embodiments. Each leaf page 600, 602, 604, 606of the B-tree index includes a data column for the matching predicateand an amount column for the screening predicate. Each leaf page 600,602, 604, 606 is sorted based on the date column, as well as on theamount column. For example, a number of keys have a same value for thematching predicate (e.g., 2003-02-02) on leaf page n 600 and leaf pagen+1 602. When skipping is used in this example, it is possible to avoidevaluating the screening predicate for many of the keys with commonmatching predicate values.

Using the traditional query evaluation techniques, for Query (2),500,000 keys are fetched and evaluated.

In this example, every day, there are 1,000,000/365=2,700 transactions,which implies that there are 2700 consecutive transaction records withthe same matching predicate column. In addition for a typical 4K pageand key length of 20 bytes, there are on average 200 keys on each page.It takes multiple skips for the matching column to change, and there isa 2% filter factor of the screening predicate.

When the techniques of embodiments of the invention are applied to theevaluation of Query (2), the average skipping interval is equal to theaverage number of keys per page divided by the number of attempts ofskipping. If a second attempt is used after the first one fails, thenthe average skipping interval is 200/2=100 keys. Among the keysqualified by the matching predicate, if 20% of them fail both attemptsof skipping, then the success rate of skipping is 80%. For each failedskip, there may be increased fetch and evaluation costs, so there may betrade-offs when choosing the number of skipping attempts. Moreover, outof 500,000 keys, the number of skips attempted is(500,000*80%/110)*(80%+4*20%)=6,400 times, whereas the conventionalfetch and evaluation is 500,000*20%=100,000 times. Therefore, the totalnumber of fetch and evaluation processes is 100,000+6,400=106,400,saving CPU time and system resources used in evaluating screenpredicates by nearly 80% compared to the conventional solution.

Another example will be provided to enhance understanding of embodimentsof the invention, but the example is not intended to limit theembodiments in any manner. With embodiments, during the index scan,certain keys with common values on a matching column may be skipped,without evaluating the screen predicate(s). Query (2) is provided againfor easy reference. Query (2) SELECT * FROM T WHERE date BETWEEN‘2003-01-01’ AND ‘2003-06-30’ <-- 50% selectivity  AND amount >= 300000;<-- 2% selectivity

Assuming that index IX1 (which is an index over the date and amountcolumns of table T) is nearly unique, the average number of keys per‘date’ is approximately 2740 (i.e., 1000000/365). Therefore, for eachkey scanned within the matching range (i.e., the first half of theB-tree), the index manager 240 is able to skip most of the 2740 keys inthe leaf pages by following the key map and/or the next page pointer ofthe leaf pages. The key map may be described as a map that indicateswhere keys are located on leaf pages.

Pseudocode A provides example pseudocode that the index manager 240 mayuse for skipping keys with common values on a matching column.

Pseudocode A

-   -   (1) Initialize variables.        -   (A) Set EK, where EK is an expected number of keys that have            common values on a matching column. For example, an initial            value of EK for the example of Query (2) is 2470). In            certain embodiments, the value of EK may be bounded by the            number of keys on one index page. The value of EK is used as            a maximum skipping interval.        -   (B) Set SKIP=FALSE, where SKIP is the start skipping            indicator.        -   (C) Set N=0, where N is a number of consecutive            false-positive keys.        -   (4) Set M=EK, where M is a skipping interval.        -   (5) Set K=0, where K is a number of skipping failures.    -   (2) Select a next key in a range defined by a matching        predicate, starting from a first key. Processing is terminated        if there are no keys left to be selected since (e.g., processing        is already at the last key in the range).    -   (3) Evaluate selected key using screening predicates.        -   (A) If the evaluation succeeds, return key to caller and go            to (2) to select next key.        -   (B) Else the evaluation failed, so increment the number of            consecutive false-positive keys by one (N=N+1).            -   (I) If N is greater than a predefined number, start the                skipping logic by setting SKIP=TRUE. Initialize the                skipping interval to a maximum value by setting M=EK.                Reset number of consecutive false-positive keys to be                zero (N=0) and reset number of skipping failure to be                zero (K=0).    -   (4) If SKIP=TRUE, then start the skipping logic.        -   (A) Skip M keys.        -   (B) Select the key after skipping.        -   (C) Check if the key is outside the range of the matching            predicate, if the matching column part of the key has been            changed from the last key selected, if the screening column            value of the key is outside of the range of the screening            predicate or if potential qualified keys have been skipped.            If any of the conditions are true, then the skipping skipped            too many keys.            -   (I) Restore the position before skipping.            -   (II) Divide skipping interval by 2 (M=M/2).            -   (III) Increment number of skipping failure by one                (K=K+1).            -   (IV) If K>predefined number, then SKIP=FALSE, go to (2)                to select the very next key, else go to (4) to perform                another skip with a smaller skipping interval.        -   (D) If skipping is not too much, then check if current key            qualifies the screening predicate.            -   (I) If yes, then return key to caller and reset M=EK,                N=0, K=0, and SKIP=false. Go to (2) to select next key                without skipping.            -   (II) If no, then go to (4) to do another skip.

Embodiments utilize the nature of a B-tree index in which keys are insorted order and pages are in sorted order, with pointers pointing to anext page, to achieve performance enhancement. Embodiments, maysignificantly reduce the CPU cost of evaluating index screeningpredicates without introducing much overhead. Embodiments autonomicallydetermine when to start and stop the skipping logic and adjust theskipping interval in order to obtain optimal performance.

In certain embodiments, the Central Processing Unit (CPU) time forcertain index scans may be reduced.

Embodiments provide a technique for evaluating index screeningpredicates, which results in the reduction of CPU time when processingqueries that include index screening predicates.

Embodiments enable skipping of many false-positive keys, withoutevaluating screening predicates. Significant reduction of CPU time isexpected for index scans with the following characteristics: poormatching selectivity (e.g. 50% in the above query); good screeningselectivity (e.g. 2% in the above query); and/or low column cardinalityon matching columns compared to full index cardinality (e.g. roughly 180days comparing with 1 million rows in the table in the above exampledescribed with respect to Query (2)).

Additional Embodiment Details

The described operations may be implemented as a method, apparatus orarticle of manufacture using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. The term “article of manufacture” as used herein refers to codeor logic implemented in a medium, where such medium may comprisehardware logic (e.g., an integrated circuit chip, Programmable GateArray (PGA), Application Specific Integrated Circuit (ASIC), etc.) or acomputer readable medium, such as magnetic storage medium (e.g., harddisk drives, floppy disks, tape, etc.), optical storage (CD-ROMs,optical disks, etc.), volatile and non-volatile memory devices (e.g.,EEPROMs; ROMs, PROMs, RAMs, DRAMs, SRAMs, firmware, programmable logic,etc.). Code in the computer readable medium is accessed and executed bya processor. The medium in which the code or logic is encoded may alsocomprise transmission signals propagating through space or atransmission media, such as an optical fiber, copper wire, etc. Thetransmission signal in which the code or logic is encoded may furthercomprise a wireless signal, satellite transmission, radio waves,infrared signals, Bluetooth, etc. The transmission signal in which thecode or logic is encoded is capable of being transmitted by atransmitting station and received by a receiving station, where the codeor logic encoded in the transmission signal may be decoded and stored inhardware or a computer readable medium at the receiving and transmittingstations or devices. Additionally, the “article of manufacture” maycomprise a combination of hardware and software components in which thecode is embodied, processed, and executed. Of course, those skilled inthe art will recognize that many modifications may be made to thisconfiguration without departing from the scope of the present invention,and that the article of manufacture may comprise any information bearingmedium known in the art.

Certain embodiments may be directed to a method for deploying computinginfrastructure by a person or automated processing integratingcomputer-readable code into a computing system, wherein the code incombination with the computing system is enabled to perform theoperations of the described embodiments.

The term logic may include, by way of example, software or hardwareand/or combinations of software and hardware.

The logic of FIGS. 3, 4A, 4B, 5A, 5B, and 5C describes specificoperations occurring in a particular order. In alternative embodiments,certain of the logic operations may be performed in a different order,modified or removed. Moreover, operations may be added to the abovedescribed logic and still conform to the described embodiments. Further,operations described herein may occur sequentially or certain operationsmay be processed in parallel, or operations described as performed by asingle process may be performed by distributed processes.

The illustrated logic of FIGS. 3, 4A, 4B, 5A, 5B, and 5C may beimplemented in software, hardware, programmable and non-programmablegate array logic or in some combination of hardware, software, or gatearray logic.

FIG. 7 illustrates an architecture 700 of a computer system that may beused in accordance with certain embodiments. Client computer 100, servercomputer 120, and/or operator console 180 may implement architecture700. The computer architecture 700 may implement a processor 702 (e.g.,a microprocessor), a memory 704 (e.g., a volatile memory device), andstorage 710 (e.g., a non-volatile storage area, such as magnetic diskdrives, optical disk drives, a tape drive, etc.). An operating system705 may execute in memory 704. The storage 710 may comprise an internalstorage device or an attached or network accessible storage. Computerprograms 706 in storage 710 may be loaded into the memory 704 andexecuted by the processor 702 in a manner known in the art. Thearchitecture further includes a network card 708 to enable communicationwith a network. An input device 712 is used to provide user input to theprocessor 702, and may include a keyboard, mouse, pen-stylus,microphone, touch sensitive display screen, or any other activation orinput mechanism known in the art. An output device 714 is capable ofrendering information from the processor 702, or other component, suchas a display monitor, printer, storage, etc. The computer architecture700 of the computer systems may include fewer components thanillustrated, additional components not illustrated herein, or somecombination of the components illustrated and additional components.

The computer architecture 700 may comprise any computing device known inthe art, such as a mainframe, server, personal computer, workstation,laptop, handheld computer, telephony device, network appliance,virtualization device, storage controller, etc. Any processor 702 andoperating system 705 known in the art may be used.

The foregoing description of embodiments has been presented for thepurposes of illustration and description. It is not intended to beexhaustive or to limit the embodiments to the precise form disclosed.Many modifications and variations are possible in light of the aboveteaching. It is intended that the scope of the embodiments be limitednot by this detailed description, but rather by the claims appendedhereto. The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theembodiments. Since many embodiments can be made without departing fromthe spirit and scope of the invention, the embodiments reside in theclaims hereinafter appended or any subsequently-filed claims, and theirequivalents.

1. A method for processing a query using an index, comprising:determining whether a number of consecutive keys that evaluate to afalse-positive when applying a screening predicate in the query exceedsa false-positive predefined value; and skipping one or more keys in theindex in response to determining that the number of consecutive keysexceeds the false-positive predefined value.
 2. The method of claim 1,further comprising: determining that index matching predicate filteringis not good and that index screening predicate filtering is good for thequery; determining that an index full key cardinality divided by anindex matching column cardinality is greater than a ratio predefinedvalue; and setting a skipping mode indicator to indicate that skippingis enabled.
 3. The method of claim 1, further comprising: determiningwhether a key in the index evaluates to a false-positive when applyingthe screening predicate in the query to the key; incrementing the numberof consecutive keys that evaluate to a false-positive in response todetermining that the key in the index does evaluate to a false-positive;and returning the key to a caller in response to determining that thekey in the index does not evaluate to a false-positive.
 4. The method ofclaim 1, further comprising: processing a next key in response todetermining that the number of consecutive keys does not exceed thefalse-positive predefined value.
 5. The method of claim 1, furthercomprising: stopping the skipping in response to determining that anumber of skipping failures is greater than a skipping failurespredefined threshold.
 6. The method of claim 1, further comprising:stopping the skipping in response to determining that the selected keyis evaluated to be qualified against the matching predicate and ascreening predicate in the query.
 7. The method of claim 1, wherein theskipping skips to a key and further comprising: determining at least oneof: (1) the skipping went beyond a last key in a matching predicaterange, (2) a matching column value of the key is not the same as amatching column value of a last evaluated key, (3) a screening columnvalue of the key is not within a range of a screening predicate in thequery, or (4) potential qualified keys have been skipped.
 8. The methodof claim 7, further comprising: backing up to a key from which theskipping was performed; adjusting a skip interval; and incrementing anumber of skipping failures.
 9. The method of claim 1, furthercomprising: determining that the skipping did not go beyond a last keyin a matching predicate range, a matching column value of the key is thesame as a matching column value of a last evaluated key, that ascreening column value of the key is within a range of a screeningpredicate in the query, and that potential qualified keys have not beenskipped.
 10. The method of claim 9, further comprising: returning thekey to a data store manager.
 11. An article of manufacture including aprogram for processing a query using an index, wherein the article ofmanufacture is operable to: determine whether a number of consecutivekeys that evaluate to a false-positive when applying a screeningpredicate in the query exceeds a false-positive predefined value; andskip one or more keys in the index in response to determining that thenumber of consecutive keys exceeds the false-positive predefined value.12. The article of manufacture of claim 11, wherein the article ofmanufacture is operable to: determine that index matching predicatefiltering is not good and that index screening predicate filtering isgood for the query; determine that an index full key cardinality dividedby an index matching column cardinality is greater than a ratiopredefined value; and set a skipping mode indicator to indicate thatskipping is enabled.
 13. The article of manufacture of claim 11, whereinthe article of manufacture is operable to: determine whether a key inthe index evaluates to a false-positive when applying the screeningpredicate in the query to the key; increment the number of consecutivekeys that evaluate to a false-positive in response to determining thatthe key in the index does evaluate to a false-positive; and return thekey to a caller in response to determining that the key in the indexdoes not evaluate to a false-positive.
 14. The article of manufacture ofclaim 11, wherein the article of manufacture is operable to: process anext key in response to determining that the number of consecutive keysdoes not exceed the false-positive predefined value.
 15. The article ofmanufacture of claim 11, wherein the article of manufacture is operableto: stop the skipping in response to determining that a number ofskipping failures is greater than a skipping failures predefinedthreshold.
 16. The article of manufacture of claim 11, wherein thearticle of manufacture is operable to: stop the skipping in response todetermining that the selected key is evaluated to be qualified againstthe matching predicate and a screening predicate in the query.
 17. Thearticle of manufacture of claim 11, wherein the skipping skips to a keyand wherein the article of manufacture is operable to: determine atleast one of: (1) the skipping went beyond a last key in a matchingpredicate range, (2) a matching column value of the key is not the sameas a matching column value of a last evaluated key, (3) a screeningcolumn value of the key is not within a range of a screening predicatein the query, or (4) potential qualified keys have been skipped.
 18. Thearticle of manufacture of claim 17, wherein the article of manufactureis operable to: back up to a key from which the skipping was performed;adjust a skip interval; and increment a number of skipping failures. 19.The article of manufacture of claim 11, wherein the article ofmanufacture is operable to: determine that the skipping did not gobeyond a last key in a matching predicate range, a matching column valueof the key is the same as a matching column value of a last evaluatedkey, that a screening column value of the key is within a range of ascreening predicate in the query, and that potential qualified keys havenot been skipped.
 20. The article of manufacture of claim 19, whereinthe article of manufacture is operable to: return the key to a datastore manager.
 21. A system for processing a query using an index,comprising: logic capable of causing operations to be performed, theoperations comprising: determining whether a number of consecutive keysthat evaluate to a false-positive when applying a screening predicate inthe query exceeds a false-positive predefined value; and skipping one ormore keys in the index in response to determining that the number ofconsecutive keys exceeds the false-positive predefined value.
 22. Thesystem of claim 21, wherein the operations further comprise: determiningthat index matching predicate filtering is not good and that indexscreening predicate filtering is good for the query; determining that anindex full key cardinality divided by an index matching columncardinality is greater than a ratio predefined value; and setting askipping mode indicator to indicate that skipping is enabled.
 23. Thesystem of claim 21, wherein the operations further comprise: determiningwhether a key in the index evaluates to a false-positive when applyingthe screening predicate in the query to the key; incrementing the numberof consecutive keys that evaluate to a false-positive in response todetermining that the key in the index does evaluate to a false-positive;and returning the key to a caller in response to determining that thekey in the index does not evaluate to a false-positive.
 24. The systemof claim 21, wherein the operations further comprise: processing a nextkey in response to determining that the number of consecutive keys doesnot exceed the false-positive predefined value.
 25. The system of claim21, wherein the operations further comprise: stopping the skipping inresponse to determining that a number of skipping failures is greaterthan a skipping failures predefined threshold.
 26. The system of claim21, wherein the operations further comprise: stopping the skipping inresponse to determining that the selected key is evaluated to bequalified against the matching predicate and a screening predicate inthe query.
 27. The system of claim 21, wherein the operation forskipping skips to a key and wherein the operations further comprise:determining at least one of: (1) the skipping went beyond a last key ina matching predicate range, (2) a matching column value of the key isnot the same as a matching column value of a last evaluated key, (3) ascreening column value of the key is not within a range of a screeningpredicate in the query, or (4) potential qualified keys have beenskipped.
 28. The system of claim 27, wherein the operations furthercomprise: backing up to a key from which the skipping was performed;adjusting a skip interval; and incrementing a number of skippingfailures.
 29. The system of claim 21, wherein the operations furthercomprise: determining that the skipping did not go beyond a last key ina matching predicate range, a matching column value of the key is thesame as a matching column value of a last evaluated key, that ascreening column value of the key is within a range of a screeningpredicate in the query, and that potential qualified keys have not beenskipped.
 30. The system of claim 29, wherein the operations furthercomprise: returning the key to a data store manager.